When moving a condition from objective A to objective B, Condition.save() was creating a fresh ProjectObjectiveCondition for the new objective while leaving the original POC (with its completion status) orphaned under the old objective. This caused a hidden/displayed POC split where the completion status was never carried over.

Changes

• framework/models.py — Condition.save() now detects when objective is being changed on an existing condition. Instead of running get_or_create against the new objective, it calls .update(objective=self.objective) on the existing POCs, preserving status in-place. The new/unchanged-objective path also incorporates the Commitment backfill logic from the next-release branch, ensuring that new conditions at new levels create matching commitments for all existing project/work-cycle combinations:

  old_objective_id = Condition.objects.values_list("objective_id", flat=True).get(pk=self.pk)
  # ...
  ProjectObjectiveCondition.objects.filter(
      condition=self, objective_id=old_objective_id
  ).update(objective=self.objective)

• framework/test_models.py — Added test_moving_condition_updates_poc_not_creates_duplicate to assert that after moving a condition: exactly one POC exists, it points to the new objective, and its status is preserved. Also includes the test_new_condition_with_new_level_backfills_commitment test from next-release that covers the Commitment backfill behaviour.

Manual checks

• If you changed the Dashboard application or the rock, have you increased the version number in rockcraft.yaml? Remember to use the same version number in README.md.

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.